Google Cloud API Gateway can now transcode standard OpenAPI specifications into remote Model Context Protocol servers. By adding a few annotation lines to an existing YAML config, your REST endpoints are exposed directly as agent tools at an /mcp endpoint. This eliminates the need to build, host, and secure a separate translation server since auth, quotas, and logging are handled by the gateway.
It is worth setting up if you already run your services behind Cloud Run and Google's API Gateway and want to connect Gemini agents without adding infrastructure. The catch is that API keys cannot protect the tool discovery endpoint in production, requiring you to configure JWT authentication instead. It is also limited to API Gateway and Apigee, so teams using custom NGINX or Envoy setups get no direct help here.
more: https://developers.googleblog.com/turn-your-rest-apis-into-mcp-tools-with-google-cloud-api-gateway/
Leave a comment